The first phase of the waterfall method is Requirements Gathering and Analysis. This phase involves analyzing the problem and communicating with the key project stakeholders to establish the requirements for the project. It includes identifying what the system needs to do and any constraints it must operate within. The success of any project is having clearly established requirements.
It is essential that the key stakeholders have input into what the system must deliver. Stakeholders typically include management (who know what they want the system to achieve for the business as a whole) and potential users (who are consulted on specific functionality). Getting a broad range of feedback is vital to avoid biases.
⚠️ The Trap: A project team only asks senior managers what they want. The managers see high-level reports, but they never use the daily functions of the system. The resulting system is unusable for the actual employees.
❓ Question 1 — Which two groups are the key stakeholders identified in the text?
Why B is correct: The text states: "This will typically include management, who will know what they want the system to achieve for the business as a whole, and potential users who would be consulted on specific functionality."
Requirements can be gathered in different ways. The choice of method is crucial to get accurate, rich data. Below are the key methods, alongside their benefits and drawbacks.
Description: Direct structured conversation with stakeholders, typically one-to-one.
➕ Benefits: Builds relationships; allows follow-up questions; picks up on non-verbal cues.
➖ Drawbacks: Very time-consuming; can make some stakeholders uncomfortable; difficult to ensure structure for easy analysis.
Description: Directly watching stakeholders in the intended environment (e.g., watching an employee use the current system).
➕ Benefits: Sees real-world environment; identifies actual current processes and challenges.
➖ Drawbacks: Can be obtrusive and disruptive; makes people uncomfortable; can lead to observer assumptions/generalisations.
Description: Reviewing existing documentation (reports, user manuals, regulatory documents).
➕ Benefits: Provides business-specific data and context; highlights key requirements/industry guidelines.
➖ Drawbacks: Quality varies; documentation may not capture actual practice; industry guidelines may be misunderstood.
Description: Group discussions and workshops involving stakeholders in a collaborative setting.
➕ Benefits: Natural idea generation; stakeholder-led; builds relationships.
➖ Drawbacks: Difficult to capture discussions for easy analysis; can be hijacked by specific personalities or agendas, leading to skewed results.
Description: Structured prewritten questions distributed in paper or online forms.
➕ Benefits: Very consistent format; easy to collate; can be distributed widely; cost-effective for large groups; participants can complete in their own time.
➖ Drawbacks: Prone to low response rates; misinterpretation of questions without clarification; lacks depth compared to interviews.
❓ Question 2 — A project team needs to gather feedback from 5,000 employees spread across the globe. They need quick, easily analyzable data and have a small budget. Which method is most appropriate?
Why C is correct: According to the text, Questionnaires are "Cost effective way to illicit feedback from large groups of participants" and have a "Very structured – format of responses will be consistent from all participants making it easier to collate and analyse." Observation, focus groups, and interviews are time-consuming, one-to-one, or too small-scale for 5,000 people.
Once information is gathered, it must be carefully analyzed and reviewed. The analysis should look for common themes and trends so data-driven decisions can be made. It is important to identify any conflicts or gaps in the requirements. Important: It should not be assumed that because a requirement hasn't been raised, it is not important. It may mean the method used to gather information was flawed or the wrong stakeholders were targeted.
❓ Question 3 — What is the recommended approach to questioning when gathering requirements?
Why C is correct: The text states: "Use a mixture of closed and open questions. Closed questions can provide quantitative data that can be more easily analysed. Open questions can provide detailed responses that lead to a deeper understanding of the problem."
🎉 You've mastered the Requirements Gathering Phase!
Recap:
• Stakeholders: Need both Management (business goals) and End-Users (specific functionality).
• Methods: Interview, Observation, Document Analysis, Focus Group, Questionnaire. Each has distinct pros/cons.
• Quality: Use mixed questions, select the right stakeholders, and choose the appropriate method for the group.
Ready to move on to Phase 2: System Design?